Impact Analysis Report

Analyzing 2 changed model(s): stg_jaffle_shop__orders, stg_stripe__payments

============================================================

stg_jaffle_shop__orders

============================================================

What Changed

Two new columns, tax_amount and gross_total, were added to the stg_jaffle_shop__orders table. The tax_amount is calculated as 8% of the order_total, and the gross_total is the sum of order_total, shipping_cost, tax_amount, minus discount_amount.

Impact Summary

The modification affects multiple downstream tables in various schemas, which are used in business-critical dashboards and reports. This requires notifying several stakeholders to ensure integration accuracy and reliability.

Affected Assets

1. Tables/Views:

   • int_orders__enriched owned by Alice Johnson
   • dim_customers owned by Eve Davis
   • fct_orders owned by Eve Davis
   • fct_daily_revenue owned by Bob Smith

2. Dashboards:

   • default on Metabase, no specific owner indicated but affects multiple key charts for business intelligence and reporting.

Risk Assessment

• Data Quality: Downstream tables utilizing the new tax_amount and gross_total columns must be tested to ensure calculations are accurate and consistent across reports.
• Compliance: The additional financial calculations might have regulatory impacts if used for financial reporting.
• Business Impact: Key surveillance dashboards and financial reporting might display incorrect data if not updated to incorporate changes correctly.

Recommended Actions

1. Notify Stakeholders:

   • Alice Johnson (Data Engineering)
   • Eve Davis (Product Analyst)
   • Bob Smith (Finance Analyst)

2. Update Downstream Assets:

   • Review and, if necessary, modify tables: int_orders__enriched, fct_orders, and fct_daily_revenue.
   • Check dashboards on jaffle-shop-metabase for accuracy.

3. Considerations:

   • Ensure any reporting using gross_total includes this in their financial summaries for correct gross calculations.
   • Validate all downstream calculations during the next reporting cycle.

============================================================

stg_stripe__payments

============================================================

What Changed

The stg_stripe__payments model has been updated to include a new column 'USD' as currency, and a filter was added to exclude transactions where billing_email ends with @test.com.

Impact Summary

The changes primarily affect downstream models and dashboards that rely on the stg_stripe__payments model for payment details. Adding the currency column could impact calculations or aggregations in downstream processes. The new filter will exclude test transactions from downstream analysis, potentially affecting insights based on transaction volume or value.

Affected Assets

1. int_orders__enriched
   • Owner: Alice Johnson
2. dim_customers
   • Owner: Eve Davis
3. fct_orders
   • Owner: Eve Davis
4. default Dashboard
   • Charts: Multiple charts impacted, no specific owner assigned.
5. fct_daily_revenue
   • Owner: Bob Smith

Risk Assessment

• Data Quality: Potential for misalignment in currency-related calculations; test transactions will no longer be included, possibly altering expected data tests.
• Compliance: Introducing a hardcoded currency may simplify currency handling but could lead to issues if multi-currency support is needed in the future.
• Business: Any dashboard or report relying on full transaction datasets might show decreased figures or volumes suddenly, impacting business intelligence outputs.

Recommended Actions

1. Notify Stakeholders:

   • Alice Johnson
   • Eve Davis
   • Bob Smith

2. Update These Assets:

   • Review calculations in int_orders__enriched
   • Analyze business rules in dim_customers and fct_orders
   • Adjust dashboard visuals from the default Dashboard
   • Check versatility in currency settings in fct_daily_revenue

3. Consider Alternatives:

   • Explore dynamic currency columns or configurations for multi-currency support.
   • Develop a flag for test transactions instead of removing them, maintaining comprehensive logging.

============================================================

Summary

============================================================